SherbyNet - /page/wikibook/entry.mu

Micron Document

`:top

`!V8`! is a `F33f`_`[JavaScript`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JavaScript_engine]`_`f and `F33f`_`[WebAssembly`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=WebAssembly]`_`f engine developed by `F33f`_`[Google`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Google]`_`f for its `F33f`_`[Chrome`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Google_Chrome]`_`f `F33f`_`[browser`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Web_browser]`_`f.`:cite-ref-v8-doc-1-2[`F5bf`_`[1`#cite-note-v8-doc-1]`_`f]`:cite-ref-comic-4-0[`F5bf`_`[4`#cite-note-comic-4]`_`f] V8 is `F33f`_`[free and open-source software`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Free_and_open-source_software]`_`f that is part of the `F33f`_`[Chromium`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Chromium_(web_browser)]`_`f project and also used separately in non-browser contexts, notably the `F33f`_`[Node.js`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Node.js]`_`f `F33f`_`[runtime system`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Runtime_system]`_`f.`:cite-ref-v8-doc-1-3[`F5bf`_`[1`#cite-note-v8-doc-1]`_`f] Other server-side JavaScript runtimes use alternative engines, such as `F33f`_`[Bun`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Bun_(software)]`_`f (which uses `F33f`_`[JavaScriptCore`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JavaScriptCore]`_`f) and Hermes (used by `F33f`_`[React Native`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=React_Native]`_`f).

>>Contents

• `F0af`_`[History`#history]`_`f

• `F0af`_`[Design`#design]`_`f

• `F0af`_`[Usage`#usage]`_`f

• `F0af`_`[See also`#see-also]`_`f

• `F0af`_`[References`#references]`_`f

• `F0af`_`[External links`#external-links]`_`f

-─

>>History

`F33f`_`[Google`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Google]`_`f created V8 for its `F33f`_`[Chrome`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Google_Chrome]`_`f browser, and both were first released in 2008.`:cite-ref-comic-4-1[`F5bf`_`[4`#cite-note-comic-4]`_`f] The lead developer of V8 was `F33f`_`[Lars Bak`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Lars_Bak_(computer_programmer)]`_`f, and it was named after the powerful `F33f`_`[car engine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=V8_engine]`_`f.`:cite-ref-5[`F5bf`_`[5`#cite-note-5]`_`f] For several years, Chrome was faster than other browsers at executing `F33f`_`[JavaScript`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=JavaScript]`_`f.`:cite-ref-6[`F5bf`_`[6`#cite-note-6]`_`f]`:cite-ref-7[`F5bf`_`[7`#cite-note-7]`_`f]`:cite-ref-8[`F5bf`_`[8`#cite-note-8]`_`f]

The V8 `F33f`_`[assembler`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Assembly_language]`_`f is based on the `F33f`_`[Strongtalk`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Strongtalk]`_`f assembler.`:cite-ref-9[`F5bf`_`[9`#cite-note-9]`_`f] On 7 December 2010, a new compiling infrastructure named Crankshaft was released, with speed improvements.`:cite-ref-10[`F5bf`_`[10`#cite-note-10]`_`f] In version 41 of Chrome in 2015, project TurboFan was added to provide more performance improvements with previously challenging workloads such as `F33f`_`[asm.js`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Asm.js]`_`f.`:cite-ref-11[`F5bf`_`[11`#cite-note-11]`_`f] Much of V8's development is strongly inspired by the `F33f`_`[Java HotSpot Virtual Machine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=HotSpot_(virtual_machine)]`_`f developed by `F33f`_`[Sun Microsystems`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Sun_Microsystems]`_`f, with the newer execution pipelines being very similar to those of HotSpot's.

Support for the new `F33f`_`[WebAssembly`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=WebAssembly]`_`f language began in 2015.`:cite-ref-12[`F5bf`_`[12`#cite-note-12]`_`f]

In 2016, the Ignition interpreter was added to V8 with the design goal of reducing the `F33f`_`[memory`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Memory_cell_(computing)]`_`f usage on small memory `F33f`_`[Android`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Android_(operating_system)]`_`f phones in comparison with TurboFan and Crankshaft.`:cite-ref-13[`F5bf`_`[13`#cite-note-13]`_`f] Ignition is a `F33f`_`[register based machine`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Register_machine]`_`f and shares a similar (albeit not the exact same) design to the templating interpreter utilized by HotSpot.

In 2017, V8 shipped a brand-new `F33f`_`[compiler`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Compiler]`_`f pipeline, consisting of Ignition (the `F33f`_`[interpreter`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Abstract_syntax_tree_interpreter]`_`f) and TurboFan (the `F33f`_`[optimizing compiler`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Program_optimization]`_`f). Starting with V8 version 5.9, Full-codegen (the early baseline compiler) and Crankshaft are no longer used in V8 for JavaScript execution, since the team believed they were no longer able to keep pace with new JavaScript language features and the optimizations those features required.`:cite-ref-14[`F5bf`_`[14`#cite-note-14]`_`f]

In 2021, a new tiered compilation pipeline was introduced with the release of the SparkPlug compiler, which supplements the existing TurboFan compiler within V8, in a direct parallel to the profiling C1 Compiler used by HotSpot.

In 2023, the Maglev `F33f`_`[SSA`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Static_single-assignment_form]`_`f-based compiler was added, which is 10 times slower than Sparkplug but 10 times faster than TurboFan, bridging the gap between Sparkplug and TurboFan for less frequently run loops that do not get "hot" enough to be optimised by TurboFan, as is the case for most web applications that spend more time interacting with the browser than in JavaScript execution. `:cite-ref-15[`F5bf`_`[15`#cite-note-15]`_`f]

>>Design

V8 first generates an `F33f`_`[abstract syntax tree`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Abstract_syntax_tree]`_`f with its own parser.`:cite-ref-16[`F5bf`_`[16`#cite-note-16]`_`f] Then, Ignition generates `F33f`_`[bytecode`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Bytecode]`_`f from this syntax tree using the internal V8 `F33f`_`[bytecode`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Bytecode]`_`f format.`:cite-ref-17[`F5bf`_`[17`#cite-note-17]`_`f] TurboFan compiles this bytecode into machine code. In other words, V8 compiles `F33f`_`[ECMAScript`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ECMAScript]`_`f directly to native `F33f`_`[machine code`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Machine_code]`_`f using `F33f`_`[just-in-time compilation`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Just-in-time_compilation]`_`f before executing it.`:cite-ref-18[`F5bf`_`[18`#cite-note-18]`_`f] The compiled code is additionally optimized (and re-optimized) dynamically at runtime, based on heuristics of the code's execution profile. Optimization techniques used include `F33f`_`[inlining`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Inlining]`_`f, `F33f`_`[elision`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Copy_elision]`_`f of expensive runtime properties, and `F33f`_`[inline caching`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Inline_caching]`_`f. The `F33f`_`[garbage collector`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Garbage_collection_(computer_science)]`_`f is a `F33f`_`[generational`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Tracing_garbage_collection]`_`f `F33f`_`[incremental`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Tracing_garbage_collection]`_`f collector.`:cite-ref-19[`F5bf`_`[19`#cite-note-19]`_`f]

>>Usage

V8 can compile to `F33f`_`[x86`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=X86_architecture]`_`f, `F33f`_`[ARM`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=ARM_architecture]`_`f or `F33f`_`[MIPS`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=MIPS_architecture]`_`f `F33f`_`[instruction set architectures`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Instruction_set_architecture]`_`f in both their `F33f`_`[32-bit`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=32-bit_computing]`_`f and `F33f`_`[64-bit`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=64-bit_computing]`_`f editions; it has additionally been ported to `F33f`_`[PowerPC`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=PowerPC]`_`f,`:cite-ref-ppc-and-z-support-20-0[`F5bf`_`[20`#cite-note-ppc-and-z-support-20]`_`f]`:cite-ref-21[`F5bf`_`[21`#cite-note-21]`_`f] and to `F33f`_`[IBM ESA/390`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=IBM_ESA/390]`_`f and `F33f`_`[z/Architecture`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Z/Architecture]`_`f,`:cite-ref-22[`F5bf`_`[22`#cite-note-22]`_`f]`:cite-ref-ppc-and-z-support-20-1[`F5bf`_`[20`#cite-note-ppc-and-z-support-20]`_`f] for use in servers.`:cite-ref-23[`F5bf`_`[23`#cite-note-23]`_`f]

V8 can be used in a browser or integrated into independent projects. V8 is used in the following software:

• `F33f`_`[Chromium`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Chromium_(web_browser)]`_`f-based `F33f`_`[web browsers`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Web_browser]`_`f - `F33f`_`[Google Chrome`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Google_Chrome]`_`f, `F33f`_`[Brave`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Brave_(web_browser)]`_`f, `F33f`_`[Opera`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Opera_(web_browser)]`_`f, `F33f`_`[Vivaldi`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Vivaldi_(web_browser)]`_`f and `F33f`_`[Microsoft Edge`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Microsoft_Edge]`_`f.

• Cloud-based environments, like `F33f`_`[Google Apps Script`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Google_Apps_Script]`_`f`:cite-ref-24[`F5bf`_`[24`#cite-note-24]`_`f]

• `F33f`_`[Couchbase`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Couchbase_Server]`_`f database server

• `F33f`_`[Deno`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Deno_(software)]`_`f runtime environment`:cite-ref-25[`F5bf`_`[25`#cite-note-25]`_`f]

• `F33f`_`[Electron`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Electron_(software_framework)]`_`f desktop application framework, used by the `F33f`_`[Atom`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Atom_(text_editor)]`_`f and `F33f`_`[Visual Studio Code`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Visual_Studio_Code]`_`f text editors

• `F33f`_`[MarkLogic`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=MarkLogic_Server]`_`f database server

• `F33f`_`[NativeScript`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=NativeScript]`_`f mobile application framework`:cite-ref-26[`F5bf`_`[26`#cite-note-26]`_`f]

• `F33f`_`[Node.js`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Node.js]`_`f runtime environment`:cite-ref-27[`F5bf`_`[27`#cite-note-27]`_`f]

>>See also

• `F33f`_`[Blink`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Blink_(browser_engine)]`_`f, the Chromium browser engine

>>References

`:cite-note-v8-doc-1`!1.`! "Documentation · V8". Google. Retrieved 3 March 2024.

`:cite-note-wikidata-e19b087eea73854757d86a770151693b4c5722e3-v20-2`!1.`! "Chrome Platform Status". Retrieved 29 June 2023.

`:cite-note-3`!2.`! "v8/LICENSE.v8 at master". Github.

`:cite-note-comic-4`!4.`! `F0af`_`[↑`#cite-ref-comic-4-0]`_`f `:citereflenssen2008`aLenssen, Philipp (1 September 2008). "Google on Google Chrome - comic book". `*Google Blogoscoped`*. Retrieved 17 August 2010.

`:cite-note-5`!5.`! `F0af`_`[↑`#cite-ref-5]`_`f "V8: an open source JavaScript engine". `*YouTube`*. Google. 15 September 2008. Retrieved 15 March 2024.

`:cite-note-6`!6.`! `F0af`_`[↑`#cite-ref-6]`_`f "Big browser comparison test: Internet Explorer vs. Firefox, Opera, Safari and Chrome". `*PC Games Hardware`*. Computec Media AG. 3 July 2009. Archived from the original on 2 May 2012. Retrieved 28 June 2010.

`:cite-note-7`!7.`! `F0af`_`[↑`#cite-ref-7]`_`f `:citerefpurdy2009`aPurdy, Kevin (11 June 2009). "Lifehacker Speed Tests: Safari 4, Chrome 2". `*`F33f`_`[Lifehacker`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Lifehacker]`_`f`*. Archived from the original on 14 April 2021. Retrieved 8 May 2021.

`:cite-note-8`!8.`! `F0af`_`[↑`#cite-ref-8]`_`f "Mozilla asks, 'Are we fast yet?'". `*Wired`*. Archived from the original on 22 June 2018. Retrieved 18 January 2019.

`:cite-note-9`!9.`! `F0af`_`[↑`#cite-ref-9]`_`f "V8 JavaScript Engine: License". `*`F33f`_`[Google Code`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Google_Code]`_`f`*. Archived from the original on 22 July 2010. Retrieved 17 August 2010.

`:cite-note-10`!10.`! `F0af`_`[↑`#cite-ref-10]`_`f "A New Crankshaft for V8". `*Chromium Blog`*. 7 December 2010. Retrieved 22 April 2011.

`:cite-note-11`!11.`! `F0af`_`[↑`#cite-ref-11]`_`f "Revving up JavaScript performance with TurboFan". 7 July 2015. Retrieved 5 March 2016.

`:cite-note-12`!12.`! `F0af`_`[↑`#cite-ref-12]`_`f "Experimental support for WebAssembly in V8". `*v8.dev`*. Retrieved 12 March 2024.

`:cite-note-13`!13.`! `F0af`_`[↑`#cite-ref-13]`_`f "BlinkOn 6 Day 1 Talk 2: Ignition - an interpreter for V8". `*`F33f`_`[YouTube`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=YouTube]`_`f`*. 26 June 2016. Archived from the original on 21 December 2021. Retrieved 2 September 2016.

`:cite-note-14`!14.`! `F0af`_`[↑`#cite-ref-14]`_`f "Launching Ignition and TurboFan". 16 May 2017. Retrieved 13 July 2017.

`:cite-note-15`!15.`! `F0af`_`[↑`#cite-ref-15]`_`f "Maglev - V8's Fastest Optimizing JIT". 5 December 2023. Retrieved 26 January 2024.

`:cite-note-16`!16.`! `F0af`_`[↑`#cite-ref-16]`_`f `:citerefverwaest2019`aVerwaest, Toon (25 March 2019). "Blazingly fast parsing, part 1: optimizing the scanner · V8". `*v8.dev`*. Archived from the original on 21 April 2021. Retrieved 1 June 2021.

`:cite-note-17`!17.`! `F0af`_`[↑`#cite-ref-17]`_`f `:citerefhinkelmann2017`aHinkelmann, Franziska (19 December 2017). "Understanding V8's Bytecode". `*Medium`*. Retrieved 17 October 2019.

`:cite-note-18`!18.`! `F0af`_`[↑`#cite-ref-18]`_`f "Firing up the Ignition interpreter · V8". `*v8.dev`*. Retrieved 30 September 2020.

`:cite-note-19`!19.`! `F0af`_`[↑`#cite-ref-19]`_`f "A game changer for interactive performance". `*blog.chromium.org`*. 21 November 2011. Retrieved 6 February 2022.

`:cite-note-ppc-and-z-support-20`!20.`! `F0af`_`[↑`#cite-ref-ppc-and-z-support-20-0]`_`f "PPC support for Google V8 goes mainstream". 30 June 2015. Archived from the original on 12 September 2015.

`:cite-note-21`!21.`! `F0af`_`[↑`#cite-ref-21]`_`f "GitHub - ibmruntimes/v8ppc: Port of Google V8 javascript engine to PowerPC®". 21 April 2019 – via GitHub.

`:cite-note-22`!22.`! `F0af`_`[↑`#cite-ref-22]`_`f "Port of Google V8 JavaScript engine to z/OS. The Linux on Z port is maintained in the community: ibmruntimes/v8z". 2 April 2019 – via GitHub.

`:cite-note-23`!23.`! `F0af`_`[↑`#cite-ref-23]`_`f "V8 Changelog v3.8.2". Archived from the original on 22 October 2012. Retrieved 23 October 2012.

`:cite-note-24`!24.`! `F0af`_`[↑`#cite-ref-24]`_`f "V8 Runtime Overview | Apps Script". `*Google for Developers`*. Retrieved 26 January 2025.

`:cite-note-25`!25.`! `F0af`_`[↑`#cite-ref-25]`_`f "A secure JavaScript/TypeScript runtime built with V8, Rust, and Tokio: denoland/deno". 8 July 2019 – via GitHub.

`:cite-note-26`!26.`! `F0af`_`[↑`#cite-ref-26]`_`f "Overview - NativeScript Docs". `*docs.nativescript.org`*. Archived from the original on 28 July 2020. Retrieved 8 July 2019.

`:cite-note-27`!27.`! `F0af`_`[↑`#cite-ref-27]`_`f `:citerefjolie-o-dell2011`aJolie O'Dell (10 March 2011). "Why Everyone Is Talking About Node". Mashable.

>>External links

Wikimedia Commons has media related to

V8 (JavaScript engine)

• Official website

`c`F0af`_`[↑ Back to top`#top]`_`f`a